Skip to content

Revert "Disable demandimport and undo other fix attempts" #31

Revert "Disable demandimport and undo other fix attempts"

Revert "Disable demandimport and undo other fix attempts" #31

Triggered via push December 14, 2023 16:29
Status Failure
Total duration 11h 6m 51s
Artifacts 3
Set Version
0s
Set Version
Build hgweb  /  publish-hgweb
47s
Build hgweb / publish-hgweb
build-hgweb  /  ...  /  deploy
build-hgweb / deploy-hgweb / deploy
Matrix: build-hgweb / deploy-hgweb / verify-published
Waiting for pending jobs
Deploy Staging  /  deploy
9s
Deploy Staging / deploy
Matrix: Deploy Staging / verify-published
Matrix: Integration tests / test
Deploy Production  /  deploy
0s
Deploy Production / deploy
Matrix: Deploy Production / verify-published
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
hahn-kev
rejected Dec 15, 2023
production

still issues with tests on staging

Annotations

3 errors and 61 warnings
Integration tests / Test windows-latest on staging.languagedepot.org
Process completed with exit code 1.
Integration tests / Test ubuntu-latest on staging.languagedepot.org
Process completed with exit code 1.
Deploy Production / deploy
The deployment was rejected or didn't satisfy other protection rules.
Build API / publish-api: backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
Build API / publish-api: backend/LexCore/Entities/ProjectUsers.cs#L8
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api: backend/LexCore/Entities/ProjectUsers.cs#L9
Non-nullable property 'Project' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api: backend/LexCore/Entities/Project.cs#L72
Non-nullable property 'Node' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api: backend/LexCore/Entities/Project.cs#L73
Non-nullable property 'Date' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api: backend/LexCore/Entities/Project.cs#L74
Non-nullable property 'Desc' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api: backend/LexCore/Entities/Project.cs#L76
Non-nullable property 'Branch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api: backend/LexCore/Entities/Project.cs#L80
Non-nullable property 'Tags' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api: backend/LexCore/Entities/Project.cs#L81
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api: backend/LexCore/Entities/Project.cs#L82
Non-nullable property 'Phase' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'Project' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'Node' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'Date' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'Desc' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'Branch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'Tags' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'Phase' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build API / publish-api
Non-nullable property 'Parents' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L72
Non-nullable property 'Node' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L73
Non-nullable property 'Date' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L74
Non-nullable property 'Desc' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L76
Non-nullable property 'Branch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L80
Non-nullable property 'Tags' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L81
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L82
Non-nullable property 'Phase' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L83
Non-nullable property 'Parents' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexCore/Entities/ProjectUsers.cs#L8
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test windows-latest on staging.languagedepot.org
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexBoxApi/Auth/Attributes/LexboxAuthAttribute.cs#L15
Nullability of reference types in type of parameter 'value' of 'void LexboxAuthAttribute.Policy.set' doesn't match implicitly implemented member 'void IAuthorizeData.Policy.set' (possibly because of nullability attributes).
Integration tests / Test windows-latest on staging.languagedepot.org: backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L115
'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes'
Integration tests / Test ubuntu-latest on staging.languagedepot.org
The support for python 2.7 will be removed on June 19. Related issue: https://github.com/actions/setup-python/issues/672
Integration tests / Test ubuntu-latest on staging.languagedepot.org
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexBoxApi/Auth/Attributes/LexboxAuthAttribute.cs#L15
Nullability of reference types in type of parameter 'value' of 'void LexboxAuthAttribute.Policy.set' doesn't match implicitly implemented member 'void IAuthorizeData.Policy.set' (possibly because of nullability attributes).
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L115
'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes'
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexCore/Entities/ProjectUsers.cs#L8
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexCore/Entities/ProjectUsers.cs#L9
Non-nullable property 'Project' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L72
Non-nullable property 'Node' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L73
Non-nullable property 'Date' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L74
Non-nullable property 'Desc' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L76
Non-nullable property 'Branch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L80
Non-nullable property 'Tags' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L81
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Integration tests / Test ubuntu-latest on staging.languagedepot.org: backend/LexCore/Entities/Project.cs#L82
Non-nullable property 'Phase' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Artifacts

Produced during runtime
Name Size
dotnet-unit-test-results Expired
12.5 KB
playwright-traces-ubuntu-latest Expired
29.2 MB
playwright-traces-windows-latest Expired
30.6 MB