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

failing BushAuthoritySystem / GenomeAuthoritySystem tests #118

Open
keturn opened this issue Aug 11, 2021 · 2 comments
Open

failing BushAuthoritySystem / GenomeAuthoritySystem tests #118

keturn opened this issue Aug 11, 2021 · 2 comments
Labels
Category: Test/QA Requests, Issues and Changes targeting tests and quality assurance Type: Bug Issues reporting and PRs fixing problems

Comments

@keturn
Copy link
Contributor

keturn commented Aug 11, 2021

See latest test report, 3 out of 4 tests fail with an NPE in GenomeAuthoritySystem.onProduceCreated.

genomeComponent.genomeId = producer.getParentPrefab().getName();

This test failure is reproducible locally.

@keturn keturn added Type: Bug Issues reporting and PRs fixing problems Category: Test/QA Requests, Issues and Changes targeting tests and quality assurance labels Aug 11, 2021
@skaldarnar
Copy link
Contributor

skaldarnar commented Aug 13, 2021

MovingBlocks/Terasology#4841 (review) fixes the NPE, at least.

With those changes, I get different failures in the tests:

image

This seems to be because producer.getParentPrefab().getName() throws an NPE.

The respective entity exists and does look like this, but it has no parent prefab 🤔

{
      "id": 31,
      "alwaysRelevant": false,
      "engine:RetainComponents": {
        "components": [
          null
        ]
      },
      "engine:Location": {
        "replicateChanges": true,
        "lastPosition": [
          0.0,
          0.0,
          0.0
        ],
        "isDirty": true,
        "lastRotation": [
          0.0,
          0.0,
          0.0,
          1.0
        ],
        "rotation": [
          0.0,
          0.0,
          0.0,
          1.0
        ],
        "scale": 1.0,
        "position": [
          0.0,
          1.0,
          0.0
        ]
      },
      "engine:Block": {
        "block": "SimpleFarming:MatureTestBush",
        "position": [
          0,
          1,
          0
        ]
      },
      "engine:Network": {
        "networkId": 9,
        "replicateMode": "RELEVANT"
      },
      "SimpleFarming:BushDefinition": {
        "currentStage": 2,
        "seedDropChances": [
          0,
          1,
          1,
          1
        ],
        "seed": "SimpleFarming:TestSeed",
        "sustainable": true,
        "growthStages": {
          "SimpleFarming:TestBush:engine:halfblock": {
            "minTime": 500,
            "maxTime": 500
          },
          "SimpleFarming:TestBush": {
            "minTime": 500,
            "maxTime": 500
          }
        },
        "produce": "SimpleFarming:TestProduce"
      }
    }

Did we change anything to how parent prefabs are computed/stored in the (recent) past? The code in that system was like that from the beginning...

@keturn
Copy link
Contributor Author

keturn commented Aug 13, 2021

The only recent activity in this module was #117, which looks vaguely similar when I squint but I don't think is the problem here.

No clue about any changes with the engine for prefabs overall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Test/QA Requests, Issues and Changes targeting tests and quality assurance Type: Bug Issues reporting and PRs fixing problems
Projects
None yet
Development

No branches or pull requests

2 participants