Skip to content

Conversation

gabrielelpidio
Copy link
Collaborator

No description provided.

@gabrielelpidio gabrielelpidio marked this pull request as draft September 30, 2025 03:20
Copy link

pkg-pr-new bot commented Sep 30, 2025

Open in StackBlitz

npm i https://pkg.pr.new/axiomhq/ai/axiom@91

commit: e78c9a4

});

afterAll(async (suite) => {
console.log('afterAll');
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
console.log('afterAll');

successCases,
erroredCases,
durationMs,
scorers: scorerNames,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

scorers names could be collected during initialization of the evaluation, I think it doesn't needed to be part of the patch request.


type EvaluationStatus = 'running' | 'completed' | 'errored' | 'cancelled';

const postCreateEvaluation = async (payload: CreateEvaluationPayload): Promise<Response | null> => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could extract the API calls to Axiom into a separate service file, there is already eval.service.ts, we can use it.

// aggregate success and scores
successCases++;
for (const s of scoreList) {
const value = Number((s as unknown as { score: number }).score);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let evalId = ''; // get traceId
let anyCaseFailed = false;
const suiteStart = performance.now();
let successCases = 0;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in afterAll() we have access to the suite along with its children, I would say its safer to loop over the suite tasks and check state of each instead of counting them this way.

Another q: are these numbers going to be used in the UI?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants