spack / spack/spack

Testing issue: fortrilinos@2.1.0%gcc11.1.0

Open
#33,111 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

test-error
Dominant language
Python
Stars
5.1k
Forks
2.5k
Avg merge
3d 4h
Merged PRs (30d)
82

Description

@aprokop @sethrj

Steps to reproduce the failure(s) or link(s) to test output(s)

The package is failing stand-alone tests in a Spack PR. More information is available at:

As well as (uo-gilgamesh):

Error message

test: calling make

make: *** No targets specified and no makefile found.  Stop.
FAILED: Command exited with status 2:
'/usr/bin/make'
make: *** No targets specified and no makefile found.  Stop.
...
Information on your system or the test runner

Runner: large-x86-prot-gitlab-runner-f79d669fb-ltnxm
OS Release: 5.4.144-69.257.amzn2.x86_64
Spack version: Spack-0.19.0.dev0 (35bc1583879735aa435b914cc0f739b3779684d1)
Repository revision: 35bc1583879735aa435b914cc0f739b3779684d1

And

Runner: uo-gilgamesh
OS Release: 4.18.0-372.9.1.el8.x86_64
Spack version: spack-0.19.0.dev0 (c1e3d638737bc04ab1fb8a46f3e6e42c04d827e0)
Repository revision: c1e3d638737bc04ab1fb8a46f3e6e42c04d827e0

Additional information

No response

General information
  • I have reported the version of Spack/Python/Platform/Runner
  • I have run spack maintainers <name-of-the-package> and @mentioned any maintainers
  • I have uploaded any available logs
  • I have searched the issues of this repo and believe this is not a duplicate

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked CDash build 1816970 and failed stand-alone tests, then compare the second build 1815629 and the reported Spack revisions. Reproduce the fortrilinos@2.1.0%gcc11.1.0 stand-alone test and trace why make runs without a makefile; done means the package's stand-alone tests complete successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.