Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failures in "CoreCLR Common Pri1 Test Build AnyOS AnyCPU" pipeline. #37466

Closed
sandreenko opened this issue Jun 5, 2020 · 4 comments · Fixed by #37468
Closed

Failures in "CoreCLR Common Pri1 Test Build AnyOS AnyCPU" pipeline. #37466

sandreenko opened this issue Jun 5, 2020 · 4 comments · Fixed by #37468
Assignees
Labels
area-Infrastructure untriaged New issue has not been triaged by the area owner

Comments

@sandreenko
Copy link
Contributor

I have rebased my changes on the top of the current master and triggered jitstress and jitstressregs, both have failed with:

/Users/runner/runners/2.169.1/work/1/s/eng/liveBuilds.targets(147,5): error : The 'libs' subset must be built before building this project. Missing artifacts: /Users/runner/runners/2.169.1/work/1/s/artifacts/bin/ref/microsoft.netcore.app/Release/ [/Users/runner/runners/2.169.1/work/1/s/src/coreclr/tests/src/Common/CoreCLRTestLibrary/CoreCLRTestLibrary.csproj]
##[error]eng/liveBuilds.targets(147,5): error : The 'libs' subset must be built before building this project. Missing artifacts: /Users/runner/runners/2.169.1/work/1/s/artifacts/bin/ref/microsoft.netcore.app/Release/

in CoreCLR Common Pri1 Test Build AnyOS AnyCPU checked that I have not seen before.
example

I think it could be caused by #37373, @safern could you take a look?

We need stress testing to be green to push two PRs that have been blocked on testing for a few days due to infrastructure issues. It would be very helpful to get this fixed/reverted before new potential disrupting infra changes.

cc @jashook @dotnet/runtime-infrastructure @CarolEidt

@ghost
Copy link

ghost commented Jun 5, 2020

Tagging subscribers to this area: @ViktorHofer
Notify danmosemsft if you want to be subscribed.

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Jun 5, 2020
@safern
Copy link
Member

safern commented Jun 5, 2020

I think it could be caused by #37373, @safern could you take a look?

I don't see how it could be caused by that, I'm inclined more towards: #37274

The warnings where the logs were not found are definitely my fault, but the Common Test Build failure, I don't see how it would be caused by my change.

@safern
Copy link
Member

safern commented Jun 5, 2020

The bug is that those ymls don't pass down liveLibrariesBuildConfig: parameter when building the test job:

jobParameters:
testGroup: jitstressregs

- ${{ if ne(parameters.liveLibrariesBuildConfig, '') }}:
- template: /eng/pipelines/common/download-artifact-step.yml
parameters:
unpackFolder: $(librariesDownloadDir)
cleanUnpackFolder: false
artifactFileName: '$(librariesBuildArtifactName)$(archiveExtension)'
artifactName: '$(librariesBuildArtifactName)'
displayName: 'live-built libraries'

@safern
Copy link
Member

safern commented Jun 5, 2020

#37468

@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants